[move-vm] Types and opcodes for closures #15171
Draft
+710
−6,878
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR implements the extensions needed in the file format for representing closures:
Function(args, result, abilities)
to represent a function typeClosPack
,ClosPackGeneric
, andClosEval
This supports bit masks for specifyinng which arguments of a function are captured when creating a closure.
Bytecode verification is extended to support the new types and opcodes. The implementation of consistency, type, and reference safety should be complete. What is missing are:
This also removes the obsolete crate
testing-infra/test-generation
. This crate already did not support many older bytecode extensions, e.g. vector ops, and is nowhere used.How Has This Been Tested?
No tests yet
Type of Change
Which Components or Systems Does This Change Impact?